Configuration Requirements to start Service Containers in batches

This topic describes the configuration requirements to be satisfied to start a set of Service Containers in batches.

The role of a System Administrator is to set the Batch size and Timeout required for the initialization of Service Containers. The following table lays out the details on the required configurations of Batch size and Timeout:

Attributes	Batch Size	Timeout
Definition	This refers to the maximum number of Service Containers that can be started simultaneously.	This refers to maximum timeout allowed for a Service Container to start before accepting another Service in the batch.
Usage	With the help of Batch size, Monitor determines the number of Service Containers that are to be started simultaneously.	With the help of timeout, Monitor determines the start of a Service Container (Monitor assumes that Service Container has started after the timeout expiry).
Storage	Stored at Monitor Service Configuration.	Stored at Monitor Container configuration.
Size	The Batch size can be changed dynamically.	The timeout period can be changed dynamically.
Value	The default value to specify a batch size is a large integer value (Integer MAX-VALUE).	The default value to specify a Timeout is 60,000 milliseconds i.e. one minute.

At the start up, on the basis of dependency list, the Monitor sorts all the configured Service Containers on its computer. Depending upon the specified batch size, it identifies the number of Service Containers that are to be started simultaneously. The pre-defined timeout governs the maximum time for initialization of each Service Container, after which the Monitor picks up the next SOAP Processor from the sorted list.
Note: A dependency list refers to a set of name spaces on which the application is dependent upon at the start up (namespaces used to invoke any Web service in the open () Web service operation of the Application connector).